-
Notifications
You must be signed in to change notification settings - Fork 1.4k
drivers: mspi: Add shim driver for sQSPI #21430
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The following west manifest projects have changed revision in this Pull Request:
✅ All manifest checks OK Note: This message is automatically posted and updated by the Manifest GitHub Action. |
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: 8a8e238ccb81acba7bc9ec631e1d6b66818d4514 more detailssdk-nrf:
zephyr:
Github labels
List of changed files detected by CI (26)Outputs:ToolchainVersion: 7cbc0036f4 Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
cd9d2e7 to
c53e0dd
Compare
|
You can find the documentation preview for this PR here. |
drivers/mspi/CMakeLists.txt
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this looks hackish, such code should be compiled/included based on a simple Kconfig selection
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, this is what the sQSPI driver requires me to set. I don't quite see how I could simplify it further on my end (I only use one Kconfig option - MSPI_NRF_SQSPI).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could sQSPI layer be structured properly?
db7becc to
73a9c9a
Compare
|
On nRF54H20, the shim driver was so far only tested with a logic analyzer using a simple application that requested TX transfers in 1-1-4 mode (to mimic what is actually needed in communication with a display). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Build system changes OK, though do agree that it could look a bit more zephyr-ish
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
Rebased. |
Add a translation layer that allows using the sQSPI soft peripheral through the Zephyr MSPI API. Also modify the manifest to pull in related changes required in sdk-zephyr. Signed-off-by: Andrzej Głąbek <[email protected]>
Add test scenario that allows testing the MSPI shim driver for the sQSPI soft peripheral on the nRF54L15 DK. Alter the existing configuration so that the SDP MSPI is enabled only when needed. Signed-off-by: Andrzej Głąbek <[email protected]>
Add NCS specific configurations for two standard Zephyr samples: spi_flash and jesd216, so that they can be run on the nRF54L15 DK using the sQSPI soft peripheral. Signed-off-by: Andrzej Głąbek <[email protected]>
|
Rebased and updated with SHA. |
Add a translation layer that allows using the sQSPI soft peripheral through the Zephyr MSPI API.
Also modify the manifest to pull in related changes required in sdk-zephyr.